Description

This PR fixes a bug in shellStart where the shellId returned from ShellTracker.registerShell() was not being used when updating the shell status, causing short-lived shell commands to remain in the "running" state even after they completed.

Changes

• Fixed shellStart.ts to use the shellId returned from registerShell() instead of generating a new one
• Added a test file to verify the fix

Related Issues

Fixes #379

Testing

• Added a new test file specifically to verify the fix
• Ran existing ShellTracker tests to ensure they still pass
• Created a manual verification script to confirm the behavior is correct

Notes

This was a subtle bug where shellStart was generating a UUID with uuidv4() but not using that ID when registering the shell. Instead, ShellTracker.registerShell() was generating its own UUID. When the shell status was later updated, it was using the first UUID, which wasn't associated with any registered shell.